Test: target RESPONSE_BODY - 069 #31
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
#27
Target test on RESPONSE_BODY. The test uses albedo's
/reflectendpoint to reflect responses. The test generates rules for phases 4 & 5, checking if 4 responses of different content-types contain a string. The 4 content-types tested are the ones present inSecResponseBodyMimeTypeand aretext/plain,text/html,text/xml, andapplication/json.Went for this test to demonstrate the framework's capability of using reflected responses and because this target is used 55 times in CRS 4.8.0 according to https://crsdoc.digitalwave.hu/?v=v4.8.0
Assessment on V2
All tests pass on V2
Assessment on V3 (using the not yet merged #24 infra)
All tests pass on V3